Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9829d029ccd4280bb696fe419e05b427428a8cd5ff8c25a84f61f6b65d74e265

Tx prefix hash: 6a512a041a20b2ef4b041542b75f2ed12433fa5f946f8df473cc43fadd69e09d
Tx public key: 25cccd63166dac0037ca067ada995b857e690408f429c4d2606dbf3815af86e4
Timestamp: 1721118390 Timestamp [UCT]: 2024-07-16 08:26:30 Age [y:d:h:m:s]: 00:255:23:55:41
Block: 1066842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182864 RingCT/type: yes/0
Extra: 0125cccd63166dac0037ca067ada995b857e690408f429c4d2606dbf3815af86e4021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4d05d6a8a725d1c875e6706d6d640aea10f8c3a4a708cfd90b561b4b70d61f8 0.600000000000 1537511 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": 1066852, "vin": [ { "gen": { "height": 1066842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4d05d6a8a725d1c875e6706d6d640aea10f8c3a4a708cfd90b561b4b70d61f8" } } ], "extra": [ 1, 37, 204, 205, 99, 22, 109, 172, 0, 55, 202, 6, 122, 218, 153, 91, 133, 126, 105, 4, 8, 244, 41, 196, 210, 96, 109, 191, 56, 21, 175, 134, 228, 2, 17, 0, 0, 0, 16, 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