Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c0605ed12a424beb65e687e669678cf6aeb6762a311b1d3311f0e55290151d9

Tx prefix hash: 2e37d483077274d25515977b2e245af915ab55589b18336519116f67f7e5c4e8
Tx public key: bdeddfb23942fc6cb14fd794d83fd6c7bccf330fd15d7e7dce9bb4fd2af15fc1
Timestamp: 1705909788 Timestamp [UCT]: 2024-01-22 07:49:48 Age [y:d:h:m:s]: 01:104:00:37:37
Block: 940695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 335482 RingCT/type: yes/0
Extra: 01bdeddfb23942fc6cb14fd794d83fd6c7bccf330fd15d7e7dce9bb4fd2af15fc10211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de342010ad6fb7da4eb848813601bffe9034817a2bad0a252eca2b82c8dfc5f8 0.600000000000 1398835 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": 940705, "vin": [ { "gen": { "height": 940695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de342010ad6fb7da4eb848813601bffe9034817a2bad0a252eca2b82c8dfc5f8" } } ], "extra": [ 1, 189, 237, 223, 178, 57, 66, 252, 108, 177, 79, 215, 148, 216, 63, 214, 199, 188, 207, 51, 15, 209, 93, 126, 125, 206, 155, 180, 253, 42, 241, 95, 193, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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