Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f972f88647ea33a37f0078693e9d3ba26244a358d9c22c80e7c9e73cbc763d02

Tx prefix hash: 1f7d1bd0021682432e89ce930655c999160a3574078dc807b514deb4a6df79bf
Tx public key: 7446dd8940c17409625e4fc3dd4a037c0fbdfd7e87486e068dc40fa400769a7c
Timestamp: 1723683096 Timestamp [UCT]: 2024-08-15 00:51:36 Age [y:d:h:m:s]: 00:219:10:54:47
Block: 1088087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156725 RingCT/type: yes/0
Extra: 017446dd8940c17409625e4fc3dd4a037c0fbdfd7e87486e068dc40fa400769a7c02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f2a0f153595384f1c432135cea0c08b8faf1bf8a94578f10208b9365c15e632 0.600000000000 1562700 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": 1088097, "vin": [ { "gen": { "height": 1088087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f2a0f153595384f1c432135cea0c08b8faf1bf8a94578f10208b9365c15e632" } } ], "extra": [ 1, 116, 70, 221, 137, 64, 193, 116, 9, 98, 94, 79, 195, 221, 74, 3, 124, 15, 189, 253, 126, 135, 72, 110, 6, 141, 196, 15, 164, 0, 118, 154, 124, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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