Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ffa50014ce7e73406cc7cd5275547082e859cb43db97831ef46043c301e7840

Tx prefix hash: 23a09e8b7ac93fdba7865a1b52394b2f6e079df5fdf5f4196d19a47b8618241e
Tx public key: 3efb3d979ca096682af3f8cbfddec9e716ed9929c239e52cb73bb8f5b3c6eaf3
Timestamp: 1750471020 Timestamp [UCT]: 2025-06-21 01:57:00 Age [y:d:h:m:s]: 00:149:21:06:54
Block: 1309442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104962 RingCT/type: yes/0
Extra: 013efb3d979ca096682af3f8cbfddec9e716ed9929c239e52cb73bb8f5b3c6eaf30211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8176616b723beae197bec129dd2bc6f1b5ab3a88b99d35bf90d4512575088d61 0.600000000000 1797059 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": 1309452, "vin": [ { "gen": { "height": 1309442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8176616b723beae197bec129dd2bc6f1b5ab3a88b99d35bf90d4512575088d61" } } ], "extra": [ 1, 62, 251, 61, 151, 156, 160, 150, 104, 42, 243, 248, 203, 253, 222, 201, 231, 22, 237, 153, 41, 194, 57, 229, 44, 183, 59, 184, 245, 179, 198, 234, 243, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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