Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2375677261083376ca83dd3644383014a4259b557339711d1aec7edbc62c8b3

Tx prefix hash: e5ec808e0744c6882e20abd929a980164cbdbc77c6e783f45ca8f96a1fc58a5c
Tx public key: 56d7f640dd802799a457a557dd4d7734bae4dd1a213a4de818152a91a24d85af
Timestamp: 1699714702 Timestamp [UCT]: 2023-11-11 14:58:22 Age [y:d:h:m:s]: 01:158:23:49:08
Block: 889383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374829 RingCT/type: yes/0
Extra: 0156d7f640dd802799a457a557dd4d7734bae4dd1a213a4de818152a91a24d85af021100000002faf35c9c000000000000000000

1 output(s) for total of 0.693593348000 dcy

stealth address amount amount idx
00: bda966cd0fe4f1b9990dc8cd60167aea79ea31cdf4399cb1171288569c0f0883 0.693593348000 1345380 of 0

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": 889393, "vin": [ { "gen": { "height": 889383 } } ], "vout": [ { "amount": 693593348, "target": { "key": "bda966cd0fe4f1b9990dc8cd60167aea79ea31cdf4399cb1171288569c0f0883" } } ], "extra": [ 1, 86, 215, 246, 64, 221, 128, 39, 153, 164, 87, 165, 87, 221, 77, 119, 52, 186, 228, 221, 26, 33, 58, 77, 232, 24, 21, 42, 145, 162, 77, 133, 175, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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