Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5173dcc206dfff9a95db8a623b859e541a5bfa447a0a82d0f1326a1f3431408

Tx prefix hash: 19d91175a5da03397458ad6e5e2ae925d83f4b57e59660e520b78c50309bc29a
Tx public key: bd40c59271f0c8a083b9b78d77bdc4758bc91bae2f676902456f56d46b273cd8
Timestamp: 1729045920 Timestamp [UCT]: 2024-10-16 02:32:00 Age [y:d:h:m:s]: 00:039:13:26:50
Block: 1132564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28232 RingCT/type: yes/0
Extra: 01bd40c59271f0c8a083b9b78d77bdc4758bc91bae2f676902456f56d46b273cd80211000000053cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d2cdd5b25abaaba8f0335783ef32fcdb57e0d136f73ed1a1dbf47da2399e00 0.600000000000 1615509 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": 1132574, "vin": [ { "gen": { "height": 1132564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d2cdd5b25abaaba8f0335783ef32fcdb57e0d136f73ed1a1dbf47da2399e00" } } ], "extra": [ 1, 189, 64, 197, 146, 113, 240, 200, 160, 131, 185, 183, 141, 119, 189, 196, 117, 139, 201, 27, 174, 47, 103, 105, 2, 69, 111, 86, 212, 107, 39, 60, 216, 2, 17, 0, 0, 0, 5, 60, 208, 252, 6, 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