Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 747da477402f270aa6df9b061fce29d539a9958b823378ce1d6f475ce54fc13c

Tx prefix hash: 306983368291d8d6b7e439df9a4c7aef8d7464e657bedf58b7b8192f7c24f42c
Tx public key: 96bfbb59eaf79d43a4f0f1494e571bb185d96a2cc79c201b9cc9f18326c78c8e
Timestamp: 1727514352 Timestamp [UCT]: 2024-09-28 09:05:52 Age [y:d:h:m:s]: 00:057:08:19:42
Block: 1119860 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40969 RingCT/type: yes/0
Extra: 0196bfbb59eaf79d43a4f0f1494e571bb185d96a2cc79c201b9cc9f18326c78c8e02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d33b71d04070e33f834cfc8a283e61896ac0fd5053b16d987cdbee451385dabc 0.600000000000 1601571 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": 1119870, "vin": [ { "gen": { "height": 1119860 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d33b71d04070e33f834cfc8a283e61896ac0fd5053b16d987cdbee451385dabc" } } ], "extra": [ 1, 150, 191, 187, 89, 234, 247, 157, 67, 164, 240, 241, 73, 78, 87, 27, 177, 133, 217, 106, 44, 199, 156, 32, 27, 156, 201, 241, 131, 38, 199, 140, 142, 2, 17, 0, 0, 0, 2, 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