Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3fdbd17fd3f33a1557c4ac5f26ff577ed00d0fd3b740f80dd81827e372823f6d

Tx prefix hash: 7b9d8f7fac12ad76e27e1a215e740538c0901ba5e623371db6919be240d13f5a
Tx public key: 9931905ba2f1a49f2efe90d69453ef314c38431e2f399853a94c5cff6efe498a
Timestamp: 1754430967 Timestamp [UCT]: 2025-08-05 21:56:07 Age [y:d:h:m:s]: 00:107:02:25:41
Block: 1341058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75521 RingCT/type: yes/0
Extra: 019931905ba2f1a49f2efe90d69453ef314c38431e2f399853a94c5cff6efe498a02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0fa7c66f5d5199f112636894232b7d4b87589a884c0bb5a89d7fc5f489d51a1 0.600000000000 1828879 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1341068, "vin": [ { "gen": { "height": 1341058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0fa7c66f5d5199f112636894232b7d4b87589a884c0bb5a89d7fc5f489d51a1" } } ], "extra": [ 1, 153, 49, 144, 91, 162, 241, 164, 159, 46, 254, 144, 214, 148, 83, 239, 49, 76, 56, 67, 30, 47, 57, 152, 83, 169, 76, 92, 255, 110, 254, 73, 138, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8