Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5089db8389455920c1688becda2d13eb3d3ad264a98578e76bf9dbabc9d35cac

Tx prefix hash: 88f6907451df544bed2789d86de14c5011bdcb92f49a52ee160a3ac5e8d7b754
Tx public key: 8ac589e9776dcf0e5d3c30e345bf8471d3f49b8165c37d03be8d474820c8d89e
Timestamp: 1731907154 Timestamp [UCT]: 2024-11-18 05:19:14 Age [y:d:h:m:s]: 00:136:20:45:20
Block: 1156179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97626 RingCT/type: yes/0
Extra: 018ac589e9776dcf0e5d3c30e345bf8471d3f49b8165c37d03be8d474820c8d89e021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d397a3ca4ebbcdfe6b9c15cb3fe3ba7c9534c192cb912b1fa48e9b25e9e0f5c7 0.600000000000 1641802 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": 1156189, "vin": [ { "gen": { "height": 1156179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d397a3ca4ebbcdfe6b9c15cb3fe3ba7c9534c192cb912b1fa48e9b25e9e0f5c7" } } ], "extra": [ 1, 138, 197, 137, 233, 119, 109, 207, 14, 93, 60, 48, 227, 69, 191, 132, 113, 211, 244, 155, 129, 101, 195, 125, 3, 190, 141, 71, 72, 32, 200, 216, 158, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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