Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67649d62d5738b071f545ee0de9d76a49de5647ba74035a18af09c97abe1b6f6

Tx prefix hash: 42e7e2116719651c558c9ad696211efb26adcf3485cf9d4ff3ae81d8e8d53e5d
Tx public key: d53925da65f8b34daaad1713b219ceedac91cf70d0a2e86a1f0459246bb73c62
Timestamp: 1653711765 Timestamp [UCT]: 2022-05-28 04:22:45 Age [y:d:h:m:s]: 02:260:14:17:00
Block: 510481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706641 RingCT/type: yes/0
Extra: 01d53925da65f8b34daaad1713b219ceedac91cf70d0a2e86a1f0459246bb73c62021100000003a8c141c5000000000000000000

1 output(s) for total of 12.490065803000 dcy

stealth address amount amount idx
00: 492cc04355c72e1b76eef1a1d09a3d7463abcc4e982eeb3c39b5921e53bc5aa8 12.490065803000 936804 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": 510491, "vin": [ { "gen": { "height": 510481 } } ], "vout": [ { "amount": 12490065803, "target": { "key": "492cc04355c72e1b76eef1a1d09a3d7463abcc4e982eeb3c39b5921e53bc5aa8" } } ], "extra": [ 1, 213, 57, 37, 218, 101, 248, 179, 77, 170, 173, 23, 19, 178, 25, 206, 237, 172, 145, 207, 112, 208, 162, 232, 106, 31, 4, 89, 36, 107, 183, 60, 98, 2, 17, 0, 0, 0, 3, 168, 193, 65, 197, 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