Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a2bc96b9f358e18bef36c346b5ad1c7982534ee03b584f27cf2ca129dab73a4

Tx prefix hash: 73b1c72de5b7f4b3e02b65e8a81919256508033b529b96545079f8879c1e4bea
Tx public key: 19f8eb66e3a5266d37904c0635c7cf850990f45e0e9aadbbc1320a0b284c8b87
Timestamp: 1744089024 Timestamp [UCT]: 2025-04-08 05:10:24 Age [y:d:h:m:s]: 00:037:04:21:44
Block: 1256755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26608 RingCT/type: yes/0
Extra: 0119f8eb66e3a5266d37904c0635c7cf850990f45e0e9aadbbc1320a0b284c8b870211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0213162d9047920c0a5749c7dd335cf0c8a85b6b7caed941980ed485f0ffeb2 0.600000000000 1743872 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": 1256765, "vin": [ { "gen": { "height": 1256755 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0213162d9047920c0a5749c7dd335cf0c8a85b6b7caed941980ed485f0ffeb2" } } ], "extra": [ 1, 25, 248, 235, 102, 227, 165, 38, 109, 55, 144, 76, 6, 53, 199, 207, 133, 9, 144, 244, 94, 14, 154, 173, 187, 193, 50, 10, 11, 40, 76, 139, 135, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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