Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f7cd436daf7dfe86bfe312254854f61bac541489a27212b724afd2c84cd9ef6

Tx prefix hash: e769be1da0f1869277ac4a39729e5ef8b328ca35b758403b2b3977b3130e9613
Tx public key: cf0d6027107945f89bca56dc50e939dba272ed0411647bab2f886826b6df6e64
Timestamp: 1622848349 Timestamp [UCT]: 2021-06-04 23:12:29 Age [y:d:h:m:s]: 03:215:03:15:16
Block: 272283 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 918159 RingCT/type: yes/0
Extra: 01cf0d6027107945f89bca56dc50e939dba272ed0411647bab2f886826b6df6e640211000006a17db3e3b6000000000000000000

1 output(s) for total of 76.880096777000 dcy

stealth address amount amount idx
00: 2946efae67b48ddf77d00cf1b17e7bd0b54250c74664d010a9320b4e8fc7e10a 76.880096777000 571493 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": 272293, "vin": [ { "gen": { "height": 272283 } } ], "vout": [ { "amount": 76880096777, "target": { "key": "2946efae67b48ddf77d00cf1b17e7bd0b54250c74664d010a9320b4e8fc7e10a" } } ], "extra": [ 1, 207, 13, 96, 39, 16, 121, 69, 248, 155, 202, 86, 220, 80, 233, 57, 219, 162, 114, 237, 4, 17, 100, 123, 171, 47, 136, 104, 38, 182, 223, 110, 100, 2, 17, 0, 0, 6, 161, 125, 179, 227, 182, 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