Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4178388f88f9e40006509d93a759292bbe48a036eabc9430603bb33d7b0ad1db

Tx prefix hash: a4f0cb1f070640323ad2092dc3393193b64e8e814cabab36ab1a749bbbe27ce4
Tx public key: 1f3ce338ca0df916a786f6c7e1b5df3b14ed465a13aa41571954608d1f6b1b6d
Timestamp: 1631398325 Timestamp [UCT]: 2021-09-11 22:12:05 Age [y:d:h:m:s]: 04:050:02:44:28
Block: 331913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1069678 RingCT/type: yes/0
Extra: 011f3ce338ca0df916a786f6c7e1b5df3b14ed465a13aa41571954608d1f6b1b6d0211000000123fc41461000000000000000000

1 output(s) for total of 48.779224449000 dcy

stealth address amount amount idx
00: 84729f2121d6725c357ec3328366f650ec710465a3db3c7494e88cafbd45915d 48.779224449000 685664 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": 331923, "vin": [ { "gen": { "height": 331913 } } ], "vout": [ { "amount": 48779224449, "target": { "key": "84729f2121d6725c357ec3328366f650ec710465a3db3c7494e88cafbd45915d" } } ], "extra": [ 1, 31, 60, 227, 56, 202, 13, 249, 22, 167, 134, 246, 199, 225, 181, 223, 59, 20, 237, 70, 90, 19, 170, 65, 87, 25, 84, 96, 141, 31, 107, 27, 109, 2, 17, 0, 0, 0, 18, 63, 196, 20, 97, 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