Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cbd9fe815ee05f67917ec421e577d407868244f6b300146bdf9c20899c0780f

Tx prefix hash: ce76b964d9ef9ba0ced548e73fd7f057e9f8d9676c79d9f0062df03aea867bf8
Tx public key: 49dbe9dbfa00e15c3f074ebab1f836a63039631f78ff6be7ec935f4880e62e22
Timestamp: 1702041080 Timestamp [UCT]: 2023-12-08 13:11:20 Age [y:d:h:m:s]: 01:140:03:22:12
Block: 908658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361332 RingCT/type: yes/0
Extra: 0149dbe9dbfa00e15c3f074ebab1f836a63039631f78ff6be7ec935f4880e62e2202110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9373994c4d3dadfb50169c373c20de81ea8928f09652f5ef068b67a43d937f2 0.600000000000 1365703 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": 908668, "vin": [ { "gen": { "height": 908658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9373994c4d3dadfb50169c373c20de81ea8928f09652f5ef068b67a43d937f2" } } ], "extra": [ 1, 73, 219, 233, 219, 250, 0, 225, 92, 63, 7, 78, 186, 177, 248, 54, 166, 48, 57, 99, 31, 120, 255, 107, 231, 236, 147, 95, 72, 128, 230, 46, 34, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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