Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c34d29212a0efa4f98a3bd9bf36e7fdb41ec9829a7d709799796262629787bd7

Tx prefix hash: 3ad8b7467ea96db827d406140a51f5ab40c2ec43cec04564d0ea74e1c6b35aa1
Tx public key: b766057b8a5faaeae80de45be1ca1c4b284be426db9db4d778338cd29175dad1
Timestamp: 1710229904 Timestamp [UCT]: 2024-03-12 07:51:44 Age [y:d:h:m:s]: 01:052:18:31:18
Block: 976572 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298709 RingCT/type: yes/0
Extra: 01b766057b8a5faaeae80de45be1ca1c4b284be426db9db4d778338cd29175dad10211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f92ee0e4a3ae7e182df3f9122e494f23b82a731e0115d2268de65c8d9cebdf 0.600000000000 1436567 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": 976582, "vin": [ { "gen": { "height": 976572 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f92ee0e4a3ae7e182df3f9122e494f23b82a731e0115d2268de65c8d9cebdf" } } ], "extra": [ 1, 183, 102, 5, 123, 138, 95, 170, 234, 232, 13, 228, 91, 225, 202, 28, 75, 40, 75, 228, 38, 219, 157, 180, 215, 120, 51, 140, 210, 145, 117, 218, 209, 2, 17, 0, 0, 0, 6, 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