Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97fee255e5f77c27b9fb59b5376e1461b9f5e7d78bf38e95b698fa38b9b5fbe0

Tx prefix hash: c3bde83256ad4deefd10ba0fb147aad65414f15e871a510179478eb0d599652a
Tx public key: 6f0afcfd4a63e877390e0c7e7b3159cac0ff2c5c43aab3e93b389c35dd1aa8c8
Timestamp: 1721738451 Timestamp [UCT]: 2024-07-23 12:40:51 Age [y:d:h:m:s]: 00:255:12:19:08
Block: 1071960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182535 RingCT/type: yes/0
Extra: 016f0afcfd4a63e877390e0c7e7b3159cac0ff2c5c43aab3e93b389c35dd1aa8c8021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45aff2cd3edff9589e435665da96064feff8e7a911738d710125ca5c80230380 0.600000000000 1544371 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": 1071970, "vin": [ { "gen": { "height": 1071960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45aff2cd3edff9589e435665da96064feff8e7a911738d710125ca5c80230380" } } ], "extra": [ 1, 111, 10, 252, 253, 74, 99, 232, 119, 57, 14, 12, 126, 123, 49, 89, 202, 192, 255, 44, 92, 67, 170, 179, 233, 59, 56, 156, 53, 221, 26, 168, 200, 2, 17, 0, 0, 0, 7, 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