Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db33952bc3b1e654a0213103b585f1ac94fc33ea3e5f896de0f2f208da03ff82

Tx prefix hash: bdca0b8cbdc6ad6441a9f0715bafda0b2fdc68fdb589c8fa65b29dda17e4c2dc
Tx public key: a3f0904f4cec963632e89b08969ccb69ec2d4f4c5e3d0ef968274474c37c2b7c
Timestamp: 1617657645 Timestamp [UCT]: 2021-04-05 21:20:45 Age [y:d:h:m:s]: 04:297:19:16:58
Block: 233967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1230906 RingCT/type: yes/0
Extra: 01a3f0904f4cec963632e89b08969ccb69ec2d4f4c5e3d0ef968274474c37c2b7c02110000003190ec05ad000000000000000000

1 output(s) for total of 102.986022873000 dcy

stealth address amount amount idx
00: 4808ab944fea72ee3bc8e0857fa7e51e110ae672c805ecfc37f444624f52afe7 102.986022873000 485739 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": 233977, "vin": [ { "gen": { "height": 233967 } } ], "vout": [ { "amount": 102986022873, "target": { "key": "4808ab944fea72ee3bc8e0857fa7e51e110ae672c805ecfc37f444624f52afe7" } } ], "extra": [ 1, 163, 240, 144, 79, 76, 236, 150, 54, 50, 232, 155, 8, 150, 156, 203, 105, 236, 45, 79, 76, 94, 61, 14, 249, 104, 39, 68, 116, 195, 124, 43, 124, 2, 17, 0, 0, 0, 49, 144, 236, 5, 173, 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