Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb06b0a4fcf9e950f026730ec17f2f2e82d4795bbb16397f1b79c946e91b045c

Tx prefix hash: 51e626ab3cd24f67a3e63e43f1276c3479777faaaa1640233e2b004274bba68c
Tx public key: bc2222f58213197ffb26e817a1cfb8571abe4f8729c806535caedd5b10d2db8e
Timestamp: 1732027944 Timestamp [UCT]: 2024-11-19 14:52:24 Age [y:d:h:m:s]: 00:004:16:00:34
Block: 1157173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3344 RingCT/type: yes/0
Extra: 01bc2222f58213197ffb26e817a1cfb8571abe4f8729c806535caedd5b10d2db8e021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60cfcb037204c8fad47ab4bdf57fd796f814e19b72bc7590a3ac4b4ae0ec6cd2 0.600000000000 1642796 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": 1157183, "vin": [ { "gen": { "height": 1157173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60cfcb037204c8fad47ab4bdf57fd796f814e19b72bc7590a3ac4b4ae0ec6cd2" } } ], "extra": [ 1, 188, 34, 34, 245, 130, 19, 25, 127, 251, 38, 232, 23, 161, 207, 184, 87, 26, 190, 79, 135, 41, 200, 6, 83, 92, 174, 221, 91, 16, 210, 219, 142, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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