Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 933deeb751f9528a5f91d715918d1cea4874e70bad54ef5d61f92e1d12b8b73b

Tx prefix hash: 431ddaf3ba40741608a78fa36e4ef1f844a82897a317ad1b6e3e6142f2245ab0
Tx public key: f0bd58e9a0d981b5c16724740ed2f7256f7f49eaed3b59726805857bfd7b67c4
Timestamp: 1702975976 Timestamp [UCT]: 2023-12-19 08:52:56 Age [y:d:h:m:s]: 01:287:10:20:14
Block: 916426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464201 RingCT/type: yes/0
Extra: 01f0bd58e9a0d981b5c16724740ed2f7256f7f49eaed3b59726805857bfd7b67c4021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b4c01eb927b4e7bdcbe2ab323277632f01410acb9d48d78b7be8120334f4bc8 0.600000000000 1373976 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": 916436, "vin": [ { "gen": { "height": 916426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b4c01eb927b4e7bdcbe2ab323277632f01410acb9d48d78b7be8120334f4bc8" } } ], "extra": [ 1, 240, 189, 88, 233, 160, 217, 129, 181, 193, 103, 36, 116, 14, 210, 247, 37, 111, 127, 73, 234, 237, 59, 89, 114, 104, 5, 133, 123, 253, 123, 103, 196, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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