Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc0f9393f84cf5a6572522f76d45783a774ff8d2eed8ae1771b95054ccd02199

Tx prefix hash: b235fd086662f0677dcb35dcf2dd2441e6937494f713575774e67b889cad7c17
Tx public key: 21403f9350d82a62d745a6c93f501cf1c09da8ac786886f7a646e483831b7bbb
Timestamp: 1577454973 Timestamp [UCT]: 2019-12-27 13:56:13 Age [y:d:h:m:s]: 04:334:14:46:07
Block: 32894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128267 RingCT/type: yes/0
Extra: 0121403f9350d82a62d745a6c93f501cf1c09da8ac786886f7a646e483831b7bbb0211000000edc3a1a09f000000000000000000

1 output(s) for total of 477.539588770000 dcy

stealth address amount amount idx
00: eab8cba3f97c1695f4c1774e80aed4d7c22472ef350fcb6f7cbeba8487c50f6e 477.539588770000 54814 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": 32904, "vin": [ { "gen": { "height": 32894 } } ], "vout": [ { "amount": 477539588770, "target": { "key": "eab8cba3f97c1695f4c1774e80aed4d7c22472ef350fcb6f7cbeba8487c50f6e" } } ], "extra": [ 1, 33, 64, 63, 147, 80, 216, 42, 98, 215, 69, 166, 201, 63, 80, 28, 241, 192, 157, 168, 172, 120, 104, 134, 247, 166, 70, 228, 131, 131, 27, 123, 187, 2, 17, 0, 0, 0, 237, 195, 161, 160, 159, 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