Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 924a823a924dae7f8cbb68f2387d0262df1b9992cfcd183bf6cb80095e3e97e2

Tx prefix hash: df6cf97812bf581e64490ab1340fdf5a65b555a5ed60a604af24bc5b597dd391
Tx public key: 1ec027fc22460118c753dab343b9bfb9684ecb1aaa6ba643b57a84a51ece13c5
Timestamp: 1715582073 Timestamp [UCT]: 2024-05-13 06:34:33 Age [y:d:h:m:s]: 00:350:08:44:56
Block: 1020952 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250430 RingCT/type: yes/0
Extra: 011ec027fc22460118c753dab343b9bfb9684ecb1aaa6ba643b57a84a51ece13c502110000000141ee1c9b000000000000000000

1 output(s) for total of 0.615590000000 dcy

stealth address amount amount idx
00: 55cd8560f6a269b89076c61a7e1a2b3fde48a18d603a210b26a6f869da8d6f39 0.615590000000 1485091 of 0

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": 1020962, "vin": [ { "gen": { "height": 1020952 } } ], "vout": [ { "amount": 615590000, "target": { "key": "55cd8560f6a269b89076c61a7e1a2b3fde48a18d603a210b26a6f869da8d6f39" } } ], "extra": [ 1, 30, 192, 39, 252, 34, 70, 1, 24, 199, 83, 218, 179, 67, 185, 191, 185, 104, 78, 203, 26, 170, 107, 166, 67, 181, 122, 132, 165, 30, 206, 19, 197, 2, 17, 0, 0, 0, 1, 65, 238, 28, 155, 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