Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e27442984c4d35777c40de0c3c4b3ea5032f1d04a94557cc78cdcdaa39d4a044

Tx prefix hash: d2eab1a2ecd57000f4802d1d4e640e93f8136578f85945889049658eb2151b01
Tx public key: e6d3e6cdd633766ba29af5e7a715e99629e1debb83e9db0bfe916a02ebc43178
Timestamp: 1694081295 Timestamp [UCT]: 2023-09-07 10:08:15 Age [y:d:h:m:s]: 01:251:04:07:54
Block: 842864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440646 RingCT/type: yes/0
Extra: 01e6d3e6cdd633766ba29af5e7a715e99629e1debb83e9db0bfe916a02ebc43178021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.989103516000 dcy

stealth address amount amount idx
00: bb859bf79771542b2f1c0b35d87bdce9cffea5013b2f5c4325c660a1984d49df 0.989103516000 1296028 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": 842874, "vin": [ { "gen": { "height": 842864 } } ], "vout": [ { "amount": 989103516, "target": { "key": "bb859bf79771542b2f1c0b35d87bdce9cffea5013b2f5c4325c660a1984d49df" } } ], "extra": [ 1, 230, 211, 230, 205, 214, 51, 118, 107, 162, 154, 245, 231, 167, 21, 233, 150, 41, 225, 222, 187, 131, 233, 219, 11, 254, 145, 106, 2, 235, 196, 49, 120, 2, 17, 0, 0, 0, 5, 230, 210, 127, 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