Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ee0a51c792546d59c1e8dc917d3ac57d59af65e646c0344db79a2fdae9b17e

Tx prefix hash: 3c09f433cbd7d3c4d9098d9e8e81a55245c07c97206d130a7797f3998852b551
Tx public key: 5956a54a7cd9ea20a61bfc535ff07c1208e2f8b1139383e78a984dfc85b1f598
Timestamp: 1705415119 Timestamp [UCT]: 2024-01-16 14:25:19 Age [y:d:h:m:s]: 01:140:22:05:21
Block: 936623 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361873 RingCT/type: yes/0
Extra: 015956a54a7cd9ea20a61bfc535ff07c1208e2f8b1139383e78a984dfc85b1f59802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4585ac435223d9a73527c97b8f8cbcba93785158224c32419a4d9bee5f67bac5 0.600000000000 1394657 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": 936633, "vin": [ { "gen": { "height": 936623 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4585ac435223d9a73527c97b8f8cbcba93785158224c32419a4d9bee5f67bac5" } } ], "extra": [ 1, 89, 86, 165, 74, 124, 217, 234, 32, 166, 27, 252, 83, 95, 240, 124, 18, 8, 226, 248, 177, 19, 147, 131, 231, 138, 152, 77, 252, 133, 177, 245, 152, 2, 17, 0, 0, 0, 3, 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