Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38fc2eea3f1d0fdf54b2c107addd27a15991c70944a1fa172ce7d1b92d2d97bd

Tx prefix hash: 5fa091f7e2b35256793d5b5bff247505e789486dee7098e92ea3ec79c5f2453c
Tx public key: 63d7ed219e906b06f48eab1f3a261e8419f3533c19154e69bbe932af5dc60a7e
Timestamp: 1648841236 Timestamp [UCT]: 2022-04-01 19:27:16 Age [y:d:h:m:s]: 02:272:18:06:01
Block: 471122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714625 RingCT/type: yes/0
Extra: 0163d7ed219e906b06f48eab1f3a261e8419f3533c19154e69bbe932af5dc60a7e0211000000025eb576c5000000000000000000

1 output(s) for total of 16.864656107000 dcy

stealth address amount amount idx
00: d0cae968b023ac271b014e73d0e8cae6ee800ed873759f5b0749d7d6fe14947f 16.864656107000 890402 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": 471132, "vin": [ { "gen": { "height": 471122 } } ], "vout": [ { "amount": 16864656107, "target": { "key": "d0cae968b023ac271b014e73d0e8cae6ee800ed873759f5b0749d7d6fe14947f" } } ], "extra": [ 1, 99, 215, 237, 33, 158, 144, 107, 6, 244, 142, 171, 31, 58, 38, 30, 132, 25, 243, 83, 60, 25, 21, 78, 105, 187, 233, 50, 175, 93, 198, 10, 126, 2, 17, 0, 0, 0, 2, 94, 181, 118, 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