Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d884e39b8ae19069b3d4510aecfa439199165c5a1bc71a7b5342c277be93946

Tx prefix hash: 9d7d62985e99c4bfd24ae57b162f87235441d3b67f5f1459f2b34361dd97cf2c
Tx public key: 2eeaa1a54347ee0d7d2b4daa960e0e75004d291a4d573fae79740f4b4a018399
Timestamp: 1712558354 Timestamp [UCT]: 2024-04-08 06:39:14 Age [y:d:h:m:s]: 01:010:08:08:16
Block: 995837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268378 RingCT/type: yes/0
Extra: 012eeaa1a54347ee0d7d2b4daa960e0e75004d291a4d573fae79740f4b4a0183990211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 425eb2218319ae880029417e163fb677d5d8bb675c77d2594958d10c170f3d68 0.600000000000 1456251 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": 995847, "vin": [ { "gen": { "height": 995837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "425eb2218319ae880029417e163fb677d5d8bb675c77d2594958d10c170f3d68" } } ], "extra": [ 1, 46, 234, 161, 165, 67, 71, 238, 13, 125, 43, 77, 170, 150, 14, 14, 117, 0, 77, 41, 26, 77, 87, 63, 174, 121, 116, 15, 75, 74, 1, 131, 153, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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