Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de1f5e4597529fea5cbb6bdb45b1733fb01dea95f7808242be2f20efff6a70e6

Tx prefix hash: fceb9f6b95af80f69f456c1f79f05edd1671335315dec8fc262329f6520d5a32
Tx public key: cd9e0a2f232cc9d643e8f01f1b77956fcf3484a8fe615aa831c7f8bbb1ff8e60
Timestamp: 1727042558 Timestamp [UCT]: 2024-09-22 22:02:38 Age [y:d:h:m:s]: 00:109:05:39:01
Block: 1115946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78096 RingCT/type: yes/0
Extra: 01cd9e0a2f232cc9d643e8f01f1b77956fcf3484a8fe615aa831c7f8bbb1ff8e6002110000000b91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 233b3199f950df589c0a1a5e234af47adebdd23afd14e7f4f0c37b15339a181c 0.600000000000 1596253 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": 1115956, "vin": [ { "gen": { "height": 1115946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "233b3199f950df589c0a1a5e234af47adebdd23afd14e7f4f0c37b15339a181c" } } ], "extra": [ 1, 205, 158, 10, 47, 35, 44, 201, 214, 67, 232, 240, 31, 27, 119, 149, 111, 207, 52, 132, 168, 254, 97, 90, 168, 49, 199, 248, 187, 177, 255, 142, 96, 2, 17, 0, 0, 0, 11, 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