Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59e1162fddccd4eb5ded121d71d966a6e655eed291c07f72fe720447822348ca

Tx prefix hash: 25fedd22f3ebbcf6a8c57e5395b697efb4f5dbaf4870816507ac01af4e73a130
Tx public key: 44b0df97943f2e5463ea9e1f28847811e4ff6e2d6db3f57749b1ad35f8940821
Timestamp: 1648462430 Timestamp [UCT]: 2022-03-28 10:13:50 Age [y:d:h:m:s]: 02:284:15:58:52
Block: 468141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 723006 RingCT/type: yes/0
Extra: 0144b0df97943f2e5463ea9e1f28847811e4ff6e2d6db3f57749b1ad35f8940821021100000001d3fcec30000000000000000000

1 output(s) for total of 17.252609187000 dcy

stealth address amount amount idx
00: 3c4b97dfd3b7d2b607c9a21ac0f50462b86cb8d97337420ff488b5ab0a1521ba 17.252609187000 886795 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": 468151, "vin": [ { "gen": { "height": 468141 } } ], "vout": [ { "amount": 17252609187, "target": { "key": "3c4b97dfd3b7d2b607c9a21ac0f50462b86cb8d97337420ff488b5ab0a1521ba" } } ], "extra": [ 1, 68, 176, 223, 151, 148, 63, 46, 84, 99, 234, 158, 31, 40, 132, 120, 17, 228, 255, 110, 45, 109, 179, 245, 119, 73, 177, 173, 53, 248, 148, 8, 33, 2, 17, 0, 0, 0, 1, 211, 252, 236, 48, 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