Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ed94eb5ed3458215bfc6b8ab9ef99ed9bf18b06c99ef2569d6be15aedf5d9fe

Tx prefix hash: c11b87b9f590a27bc04e34a9ef45e63f9f186b538755e052d2f9491c34df4472
Tx public key: a7d4501c1a0fe02fffaafc9996f4a7d54f55bd447f466733592a8537c802868d
Timestamp: 1728947302 Timestamp [UCT]: 2024-10-14 23:08:22 Age [y:d:h:m:s]: 01:025:04:30:41
Block: 1131737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276361 RingCT/type: yes/0
Extra: 01a7d4501c1a0fe02fffaafc9996f4a7d54f55bd447f466733592a8537c802868d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c7531ec2c01da9be6a514f74f09006a3c64a8c6b74a0583637b5fea0205b311 0.600000000000 1614642 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": 1131747, "vin": [ { "gen": { "height": 1131737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c7531ec2c01da9be6a514f74f09006a3c64a8c6b74a0583637b5fea0205b311" } } ], "extra": [ 1, 167, 212, 80, 28, 26, 15, 224, 47, 255, 170, 252, 153, 150, 244, 167, 213, 79, 85, 189, 68, 127, 70, 103, 51, 89, 42, 133, 55, 200, 2, 134, 141, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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