Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fa00c4a2c0f0dea40d5e5982651d108a129edc0cba506cfa350376518cc2583

Tx prefix hash: 8e480bae80d393be46a999551dac9381d2abb44e9a6f604a18999e8c3385af7b
Tx public key: c1875f4b7ab3682a2409320cb691103fcf43b7c52a0eda15f3d5de5146c9e102
Timestamp: 1577785939 Timestamp [UCT]: 2019-12-31 09:52:19 Age [y:d:h:m:s]: 05:155:00:10:27
Block: 35581 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1260685 RingCT/type: yes/0
Extra: 01c1875f4b7ab3682a2409320cb691103fcf43b7c52a0eda15f3d5de5146c9e1020211000000104943cd9f000000000000000000

1 output(s) for total of 467.849565776000 dcy

stealth address amount amount idx
00: f4d93ca6e513f3e0c6bffe458ee64257b8cf5a0488648125228ca5a05bfc1939 467.849565776000 60080 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": 35591, "vin": [ { "gen": { "height": 35581 } } ], "vout": [ { "amount": 467849565776, "target": { "key": "f4d93ca6e513f3e0c6bffe458ee64257b8cf5a0488648125228ca5a05bfc1939" } } ], "extra": [ 1, 193, 135, 95, 75, 122, 179, 104, 42, 36, 9, 50, 12, 182, 145, 16, 63, 207, 67, 183, 197, 42, 14, 218, 21, 243, 213, 222, 81, 70, 201, 225, 2, 2, 17, 0, 0, 0, 16, 73, 67, 205, 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