Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 851046ddf45d952f3d4a37045c9f901c131b12dd03a5fab9ef79363bc4fb668f

Tx prefix hash: 361a488023ff0a50ecdcd9e57893df4b401234bda80ded3f9d1dc852c4a6755c
Tx public key: dc5a73511b1033aa3065c1e4fbcb36a88cefa2102689a0788e2c08a97a47ad66
Timestamp: 1725792554 Timestamp [UCT]: 2024-09-08 10:49:14 Age [y:d:h:m:s]: 00:077:02:45:12
Block: 1105581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55134 RingCT/type: yes/0
Extra: 01dc5a73511b1033aa3065c1e4fbcb36a88cefa2102689a0788e2c08a97a47ad6602110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06a7a7b82184c2679d6e3a93275495eea3bc98a6c254cc925520786d2015b620 0.600000000000 1582960 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": 1105591, "vin": [ { "gen": { "height": 1105581 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06a7a7b82184c2679d6e3a93275495eea3bc98a6c254cc925520786d2015b620" } } ], "extra": [ 1, 220, 90, 115, 81, 27, 16, 51, 170, 48, 101, 193, 228, 251, 203, 54, 168, 140, 239, 162, 16, 38, 137, 160, 120, 142, 44, 8, 169, 122, 71, 173, 102, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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