Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0abb8fb0e71806b745c2a95b2c725098a86d3b6872ddf8fed8ef9e49e6ef655

Tx prefix hash: cabb92c6d55e548825423a8810f445b58dc1790645ba0fb590e09336023768d6
Tx public key: b1b869a0b9ffe1911c46f700f740e1b3d89173797bc590e8f8a027679c22e54e
Timestamp: 1683616533 Timestamp [UCT]: 2023-05-09 07:15:33 Age [y:d:h:m:s]: 02:226:17:04:52
Block: 756175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 681910 RingCT/type: yes/0
Extra: 01b1b869a0b9ffe1911c46f700f740e1b3d89173797bc590e8f8a027679c22e54e021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.916366260000 dcy

stealth address amount amount idx
00: 658a301b4261560368787a3647a924a63add3642c79eb3cd9a8b152a9661da5f 1.916366260000 1204526 of 0

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": 756185, "vin": [ { "gen": { "height": 756175 } } ], "vout": [ { "amount": 1916366260, "target": { "key": "658a301b4261560368787a3647a924a63add3642c79eb3cd9a8b152a9661da5f" } } ], "extra": [ 1, 177, 184, 105, 160, 185, 255, 225, 145, 28, 70, 247, 0, 247, 64, 225, 179, 216, 145, 115, 121, 123, 197, 144, 232, 248, 160, 39, 103, 156, 34, 229, 78, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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