Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e975044e44dbcbeeacd0700ba38ba54c8f92d4df020106355d60ef11160debb

Tx prefix hash: 0a3c84c55ed52ea3c14984de73f569484d6268f895a91dd5526e703734936416
Tx public key: c17693d661d6913b0b39a3aa3ccbc10343599a82c49b6c7d99c4c3dfad6d0fe3
Timestamp: 1705670940 Timestamp [UCT]: 2024-01-19 13:29:00 Age [y:d:h:m:s]: 01:037:15:31:16
Block: 938726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287982 RingCT/type: yes/0
Extra: 01c17693d661d6913b0b39a3aa3ccbc10343599a82c49b6c7d99c4c3dfad6d0fe30211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e19979085df4e221f908a7c627fe9a1e2f64f7b0bba5e0cefacecc4dbdb94d9d 0.600000000000 1396804 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": 938736, "vin": [ { "gen": { "height": 938726 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e19979085df4e221f908a7c627fe9a1e2f64f7b0bba5e0cefacecc4dbdb94d9d" } } ], "extra": [ 1, 193, 118, 147, 214, 97, 214, 145, 59, 11, 57, 163, 170, 60, 203, 193, 3, 67, 89, 154, 130, 196, 155, 108, 125, 153, 196, 195, 223, 173, 109, 15, 227, 2, 17, 0, 0, 0, 7, 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