Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a21919951f4ae36b573866d94bf55d9b2bbd1e9edaf3d72fd71fb54957b00ee

Tx prefix hash: e4efab9330a138054803b013c882fc751f89c38a45b2f54895cdabc9b8efdaf0
Tx public key: bcb300cfa3374a951479d3d343102609c25a8378f34f8e465ff3f5a608d4dd32
Timestamp: 1732640926 Timestamp [UCT]: 2024-11-26 17:08:46 Age [y:d:h:m:s]: 00:118:04:30:39
Block: 1162258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84264 RingCT/type: yes/0
Extra: 01bcb300cfa3374a951479d3d343102609c25a8378f34f8e465ff3f5a608d4dd32021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e5b517843ce5064ca904e1508c3053978e5a28937ebbd99314f3d7a98e5e2df 0.600000000000 1647913 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": 1162268, "vin": [ { "gen": { "height": 1162258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e5b517843ce5064ca904e1508c3053978e5a28937ebbd99314f3d7a98e5e2df" } } ], "extra": [ 1, 188, 179, 0, 207, 163, 55, 74, 149, 20, 121, 211, 211, 67, 16, 38, 9, 194, 90, 131, 120, 243, 79, 142, 70, 95, 243, 245, 166, 8, 212, 221, 50, 2, 17, 0, 0, 0, 4, 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