Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8bf7322d96b5df529893cd088c4b0e92f740418a107cb6e9ea32c91b5b14e800

Tx prefix hash: 6d1c31955e6fe6ea54f6556cb94780a5260a1b554dbb870a353b00c6841aaf0d
Tx public key: b82eae2de3f806d98d204fa4338a6b0e62cc64d69702becc073da1518d938a78
Timestamp: 1724522514 Timestamp [UCT]: 2024-08-24 18:01:54 Age [y:d:h:m:s]: 00:095:11:31:44
Block: 1095066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68276 RingCT/type: yes/0
Extra: 01b82eae2de3f806d98d204fa4338a6b0e62cc64d69702becc073da1518d938a78021100000003e337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be4fb21559c565b161f63a328240191cbf105f5b787a16e3b95ed97cd3e480bb 0.600000000000 1570203 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": 1095076, "vin": [ { "gen": { "height": 1095066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be4fb21559c565b161f63a328240191cbf105f5b787a16e3b95ed97cd3e480bb" } } ], "extra": [ 1, 184, 46, 174, 45, 227, 248, 6, 217, 141, 32, 79, 164, 51, 138, 107, 14, 98, 204, 100, 214, 151, 2, 190, 204, 7, 61, 161, 81, 141, 147, 138, 120, 2, 17, 0, 0, 0, 3, 227, 55, 53, 142, 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