Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3225236be2c82b54444143e14d633d475a70505f971adf0d1e8cab2bcf336d69

Tx prefix hash: 1da4e84268f746747ac97e9c010a3257ca1baabe093368710f55c311c8bc67d0
Tx public key: 29dd53d703923e1cf728f964da9fb191b34c39c4392e9c6f5adfd2940761db85
Timestamp: 1710560865 Timestamp [UCT]: 2024-03-16 03:47:45 Age [y:d:h:m:s]: 01:262:23:00:16
Block: 979314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446658 RingCT/type: yes/0
Extra: 0129dd53d703923e1cf728f964da9fb191b34c39c4392e9c6f5adfd2940761db850211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fdef01d47eeb62875da4859d008f0916153ee4dc9be489fba467be6bc13facf 0.600000000000 1439347 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": 979324, "vin": [ { "gen": { "height": 979314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fdef01d47eeb62875da4859d008f0916153ee4dc9be489fba467be6bc13facf" } } ], "extra": [ 1, 41, 221, 83, 215, 3, 146, 62, 28, 247, 40, 249, 100, 218, 159, 177, 145, 179, 76, 57, 196, 57, 46, 156, 111, 90, 223, 210, 148, 7, 97, 219, 133, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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