Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d6913d0ffa8b0e764f712c7f7ad7e24c51561bdbdaeb6ac31a5c92ba52fa0cb

Tx prefix hash: 5f36e01ace1a004729d7080d63a8f580772a9bd6ccdcb1b7fc1426b3ab65a8ad
Tx public key: b3fba73bdfb10cc0f8ae61ab9b50d1b44e3aa6462f6ba09c19f3ba92a6d199a3
Timestamp: 1705999406 Timestamp [UCT]: 2024-01-23 08:43:26 Age [y:d:h:m:s]: 01:087:15:09:18
Block: 941450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323744 RingCT/type: yes/0
Extra: 01b3fba73bdfb10cc0f8ae61ab9b50d1b44e3aa6462f6ba09c19f3ba92a6d199a302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecdd1128b15b01d33790203e19e7201be02a8b9770ae460e4922fc08ae02f9b5 0.600000000000 1399600 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": 941460, "vin": [ { "gen": { "height": 941450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecdd1128b15b01d33790203e19e7201be02a8b9770ae460e4922fc08ae02f9b5" } } ], "extra": [ 1, 179, 251, 167, 59, 223, 177, 12, 192, 248, 174, 97, 171, 155, 80, 209, 180, 78, 58, 166, 70, 47, 107, 160, 156, 25, 243, 186, 146, 166, 209, 153, 163, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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