Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fd880d6d02c2d8e12f11494f9e326f77609324e80b9a065a58f3be13d0ab443

Tx prefix hash: 450dec8d9e4d75cad899fcde6ad47e71a20e42c6e12787a5a82ce95e20428897
Tx public key: 1b567cda40b161c38ad2ebfe0c0ad52442332ab96bb8cde5e2f535b5fdd49f39
Timestamp: 1684782653 Timestamp [UCT]: 2023-05-22 19:10:53 Age [y:d:h:m:s]: 01:338:07:28:18
Block: 765848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503012 RingCT/type: yes/0
Extra: 011b567cda40b161c38ad2ebfe0c0ad52442332ab96bb8cde5e2f535b5fdd49f39021100000001faf35c9c000000000000000000

1 output(s) for total of 1.780032113000 dcy

stealth address amount amount idx
00: 5457bd0e54d68d729805ea0e470329209dab8a0212a0eb5a69b07aa0db3daaf4 1.780032113000 1214857 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": 765858, "vin": [ { "gen": { "height": 765848 } } ], "vout": [ { "amount": 1780032113, "target": { "key": "5457bd0e54d68d729805ea0e470329209dab8a0212a0eb5a69b07aa0db3daaf4" } } ], "extra": [ 1, 27, 86, 124, 218, 64, 177, 97, 195, 138, 210, 235, 254, 12, 10, 213, 36, 66, 51, 42, 185, 107, 184, 205, 229, 226, 245, 53, 181, 253, 212, 159, 57, 2, 17, 0, 0, 0, 1, 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