Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2191b10c9c6653040f3ef243b61ec62baa55d235432b3532ca50da74833f23b5

Tx prefix hash: a0f2a2e52434f4cfcb476659f602e27a636b5e315021914482292241a5e95dd2
Tx public key: 3bc2771ab570d7ac861850e5860d5ac3413c449084c0774acedd2834f32c9b4c
Timestamp: 1588737273 Timestamp [UCT]: 2020-05-06 03:54:33 Age [y:d:h:m:s]: 04:339:04:13:58
Block: 99134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158438 RingCT/type: yes/0
Extra: 013bc2771ab570d7ac861850e5860d5ac3413c449084c0774acedd2834f32c9b4c021100000160a86a1a65000000000000000000

1 output(s) for total of 288.090321799000 dcy

stealth address amount amount idx
00: e765b50e055c6eb8a07da1ae4c24e998987d3057e49020d9c6f761ff13f51f26 288.090321799000 174980 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": 99144, "vin": [ { "gen": { "height": 99134 } } ], "vout": [ { "amount": 288090321799, "target": { "key": "e765b50e055c6eb8a07da1ae4c24e998987d3057e49020d9c6f761ff13f51f26" } } ], "extra": [ 1, 59, 194, 119, 26, 181, 112, 215, 172, 134, 24, 80, 229, 134, 13, 90, 195, 65, 60, 68, 144, 132, 192, 119, 74, 206, 221, 40, 52, 243, 44, 155, 76, 2, 17, 0, 0, 1, 96, 168, 106, 26, 101, 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