Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81754ff9cb8c3cadb26ba21cc396ed7a530a42cc2a4a21e7479379f19f6ff582

Tx prefix hash: be11857f4e0aaf0eb3bb1a3ebe31187bc59356397104c1ef6a741dc4234d2122
Tx public key: a5225e73ce5cf4569c745467e8f7220df39e96b2104c4073ccf3b4ffe5f068e5
Timestamp: 1735503996 Timestamp [UCT]: 2024-12-29 20:26:36 Age [y:d:h:m:s]: 00:100:08:10:06
Block: 1185949 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71509 RingCT/type: yes/0
Extra: 01a5225e73ce5cf4569c745467e8f7220df39e96b2104c4073ccf3b4ffe5f068e50211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71584dfcff76a018e36098d8d6a7374ba2b4ef5f8d0f8d29dbd37e87b22208f1 0.600000000000 1672424 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": 1185959, "vin": [ { "gen": { "height": 1185949 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71584dfcff76a018e36098d8d6a7374ba2b4ef5f8d0f8d29dbd37e87b22208f1" } } ], "extra": [ 1, 165, 34, 94, 115, 206, 92, 244, 86, 156, 116, 84, 103, 232, 247, 34, 13, 243, 158, 150, 178, 16, 76, 64, 115, 204, 243, 180, 255, 229, 240, 104, 229, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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