Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74dac7984f851c1d1f0d44fd9ba6e8137bea387977a7f5b61eab284f6ab45583

Tx prefix hash: 6c76502923211924d5d5fb44b5c299ff86a2bfef5a9e78c1ef5d670676760b27
Tx public key: 2bff7148223351b8d88b20a51853d610c5cf5da1529ec9f29554170d1bbff476
Timestamp: 1710693536 Timestamp [UCT]: 2024-03-17 16:38:56 Age [y:d:h:m:s]: 01:234:04:01:32
Block: 980420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 426033 RingCT/type: yes/0
Extra: 012bff7148223351b8d88b20a51853d610c5cf5da1529ec9f29554170d1bbff47602110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70f7aba172323370fc28bfaf1f82dbf8e0631d3f369d3bd50021d9357e9dd82a 0.600000000000 1440485 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": 980430, "vin": [ { "gen": { "height": 980420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70f7aba172323370fc28bfaf1f82dbf8e0631d3f369d3bd50021d9357e9dd82a" } } ], "extra": [ 1, 43, 255, 113, 72, 34, 51, 81, 184, 216, 139, 32, 165, 24, 83, 214, 16, 197, 207, 93, 161, 82, 158, 201, 242, 149, 84, 23, 13, 27, 191, 244, 118, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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