Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438922d0de142c15d0a0ecf2f44f900591279a771185f89e52dd868f81749708

Tx prefix hash: 121bd9a9f86d407a5e430bb3d5e0b33aac19a75d9c48432bd1a98ec76db0ea8a
Tx public key: a7bf5977411d6f5fb57b7ddf2c7003c53dce9a59e85f55bdafbdf0385185ccdf
Timestamp: 1687404011 Timestamp [UCT]: 2023-06-22 03:20:11 Age [y:d:h:m:s]: 01:299:08:17:16
Block: 787569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475111 RingCT/type: yes/0
Extra: 01a7bf5977411d6f5fb57b7ddf2c7003c53dce9a59e85f55bdafbdf0385185ccdf0211000000044b8f5122000000000000000000

1 output(s) for total of 1.508193677000 dcy

stealth address amount amount idx
00: 3e7611a7d81fee1528a65d9906a27f377ecefd9f758b4bc45712802294105897 1.508193677000 1237632 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": 787579, "vin": [ { "gen": { "height": 787569 } } ], "vout": [ { "amount": 1508193677, "target": { "key": "3e7611a7d81fee1528a65d9906a27f377ecefd9f758b4bc45712802294105897" } } ], "extra": [ 1, 167, 191, 89, 119, 65, 29, 111, 95, 181, 123, 125, 223, 44, 112, 3, 197, 61, 206, 154, 89, 232, 95, 85, 189, 175, 189, 240, 56, 81, 133, 204, 223, 2, 17, 0, 0, 0, 4, 75, 143, 81, 34, 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