Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3adccce77b6875be985cdda1f314ecce9b7d79c7e066746c51054cdc14ef781b

Tx prefix hash: 46c4f037b412b82ce293eebb99cadc421a42dcf869b9a6dbf3cb75c2974e5334
Tx public key: 663e9b65d4b888ce825d6741a056a5d4d714e3059577aeeb1eb2032c9c9d1a3e
Timestamp: 1580117637 Timestamp [UCT]: 2020-01-27 09:33:57 Age [y:d:h:m:s]: 05:008:05:05:30
Block: 53843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1156708 RingCT/type: yes/0
Extra: 01663e9b65d4b888ce825d6741a056a5d4d714e3059577aeeb1eb2032c9c9d1a3e0211000000012264afe6000000000000000000

1 output(s) for total of 407.002069082000 dcy

stealth address amount amount idx
00: feb9c627ab7c9a5afed36243f4fc0567d31fdf56480e72a05ea422b3534c12f5 407.002069082000 99789 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": 53853, "vin": [ { "gen": { "height": 53843 } } ], "vout": [ { "amount": 407002069082, "target": { "key": "feb9c627ab7c9a5afed36243f4fc0567d31fdf56480e72a05ea422b3534c12f5" } } ], "extra": [ 1, 102, 62, 155, 101, 212, 184, 136, 206, 130, 93, 103, 65, 160, 86, 165, 212, 215, 20, 227, 5, 149, 119, 174, 235, 30, 178, 3, 44, 156, 157, 26, 62, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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