Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc9ec05135a17f86624df527b2db2c4e9fbdf24716503ba53224494ed2ba4f3f

Tx prefix hash: f18e77a0bd57881454c8df02af7c94ae50a7787166f27eb08281cc21924071e2
Tx public key: 190d78a1124bcbe8d821d160da2b7caaa5ed68129c8faff1607f273b1ff8f7db
Timestamp: 1722715391 Timestamp [UCT]: 2024-08-03 20:03:11 Age [y:d:h:m:s]: 00:160:00:18:35
Block: 1080061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114485 RingCT/type: yes/0
Extra: 01190d78a1124bcbe8d821d160da2b7caaa5ed68129c8faff1607f273b1ff8f7db02110000001fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd4739ced9369d63f7ddd645958dc3f5f51f855e14f33dff997b5ed35fd84ce6 0.600000000000 1553278 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": 1080071, "vin": [ { "gen": { "height": 1080061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd4739ced9369d63f7ddd645958dc3f5f51f855e14f33dff997b5ed35fd84ce6" } } ], "extra": [ 1, 25, 13, 120, 161, 18, 75, 203, 232, 216, 33, 209, 96, 218, 43, 124, 170, 165, 237, 104, 18, 156, 143, 175, 241, 96, 127, 39, 59, 31, 248, 247, 219, 2, 17, 0, 0, 0, 31, 233, 20, 221, 21, 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