Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ab11f3ef4b853a924a540f537e091161fd7997a648d7f2ef69239fb9fe5466b

Tx prefix hash: 27e60eafce6010d2adb1f85cc9dafffa3d2305be1065352228d8b5f03c75c041
Tx public key: 5f067f0de9166ad619b9420f8b8e9fc7f54948e16f438ff1be27f2136ef921d2
Timestamp: 1736900392 Timestamp [UCT]: 2025-01-15 00:19:52 Age [y:d:h:m:s]: 00:154:16:44:56
Block: 1197517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110273 RingCT/type: yes/0
Extra: 015f067f0de9166ad619b9420f8b8e9fc7f54948e16f438ff1be27f2136ef921d2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e99b30e7d903b65272620fe2c13d26f5e6de01b78f7d333a73ecfc2971b6ab17 0.600000000000 1684126 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": 1197527, "vin": [ { "gen": { "height": 1197517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e99b30e7d903b65272620fe2c13d26f5e6de01b78f7d333a73ecfc2971b6ab17" } } ], "extra": [ 1, 95, 6, 127, 13, 233, 22, 106, 214, 25, 185, 66, 15, 139, 142, 159, 199, 245, 73, 72, 225, 111, 67, 143, 241, 190, 39, 242, 19, 110, 249, 33, 210, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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