Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87f3dca96ce01cdccf8c5d71daf0f3b108d4c6f725e83308e1cde106bf41f1e2

Tx prefix hash: 58a65d456cd121f8518d4060f4364ceef94eb846aca90a5cc51da9ab8f494a7a
Tx public key: db6438dbaa4c9fb65b08e6b6563c2a4248edc6b48edbe916ea8ef61b532230ab
Timestamp: 1716231092 Timestamp [UCT]: 2024-05-20 18:51:32 Age [y:d:h:m:s]: 00:281:18:29:26
Block: 1026317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201358 RingCT/type: yes/0
Extra: 01db6438dbaa4c9fb65b08e6b6563c2a4248edc6b48edbe916ea8ef61b532230ab02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1030381ac91fc5bda236c63d0d0ffdcf775aa4a86d882cd168704a2ef52650e 0.600000000000 1493332 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": 1026327, "vin": [ { "gen": { "height": 1026317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1030381ac91fc5bda236c63d0d0ffdcf775aa4a86d882cd168704a2ef52650e" } } ], "extra": [ 1, 219, 100, 56, 219, 170, 76, 159, 182, 91, 8, 230, 182, 86, 60, 42, 66, 72, 237, 198, 180, 142, 219, 233, 22, 234, 142, 246, 27, 83, 34, 48, 171, 2, 17, 0, 0, 0, 1, 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