Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebbf8276f259c35f27eada37fd6653f15d22b632a3b55a8e764ee5e202f5038b

Tx prefix hash: 38b1d9af40774270abc9b718dd5924aa78eafced14b51ab5782ce4571a860f86
Tx public key: accb473e2b05fcc41a2e52e8af560b47af0a21074e52adb01f3b91d4c1dbf52e
Timestamp: 1728003801 Timestamp [UCT]: 2024-10-04 01:03:21 Age [y:d:h:m:s]: 00:051:16:42:23
Block: 1123914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 36927 RingCT/type: yes/0
Extra: 01accb473e2b05fcc41a2e52e8af560b47af0a21074e52adb01f3b91d4c1dbf52e02110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3bda2992a003392bf652935071ed391204cdfd8de4a4dc06ff075568d7a7c44 0.600000000000 1606463 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": 1123924, "vin": [ { "gen": { "height": 1123914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3bda2992a003392bf652935071ed391204cdfd8de4a4dc06ff075568d7a7c44" } } ], "extra": [ 1, 172, 203, 71, 62, 43, 5, 252, 196, 26, 46, 82, 232, 175, 86, 11, 71, 175, 10, 33, 7, 78, 82, 173, 176, 31, 59, 145, 212, 193, 219, 245, 46, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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