Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 212a1ebc365035be7d4ffba009bda3c71139cb916e7a1f9cab3e57cef4fca5e7

Tx prefix hash: f42e33e785506530ffb095c7bbd15e5b1b77f75f92bc8790fb3e55a75ee5c6e6
Tx public key: 4f4dc6549cddb8a3f048411689c6f0cc6033ee81e32b752ef606197f7662abce
Timestamp: 1577740237 Timestamp [UCT]: 2019-12-30 21:10:37 Age [y:d:h:m:s]: 05:003:21:18:19
Block: 35328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1152713 RingCT/type: yes/0
Extra: 014f4dc6549cddb8a3f048411689c6f0cc6033ee81e32b752ef606197f7662abce0211000000074943cd9f000000000000000000

1 output(s) for total of 468.790981805000 dcy

stealth address amount amount idx
00: a917207e29d6ae2f3a21ed37fbcb16bda4194f494360e898a0a06818fcc1d284 468.790981805000 59502 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": 35338, "vin": [ { "gen": { "height": 35328 } } ], "vout": [ { "amount": 468790981805, "target": { "key": "a917207e29d6ae2f3a21ed37fbcb16bda4194f494360e898a0a06818fcc1d284" } } ], "extra": [ 1, 79, 77, 198, 84, 156, 221, 184, 163, 240, 72, 65, 22, 137, 198, 240, 204, 96, 51, 238, 129, 227, 43, 117, 46, 246, 6, 25, 127, 118, 98, 171, 206, 2, 17, 0, 0, 0, 7, 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