Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03474fa0fed8d62efadafdd2ef62d6a0ae0b6d511383d15948640c7838772c6b

Tx prefix hash: bea89f00afadfbbc0e34ee9929a25cd54d6d360372615a26800e248b2f09f07a
Tx public key: fea9e8328f368f7258bb3b87d861b670a86d9aa6fd7d20cf83cba07aafdc96f8
Timestamp: 1693991848 Timestamp [UCT]: 2023-09-06 09:17:28 Age [y:d:h:m:s]: 01:210:16:32:04
Block: 842111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411684 RingCT/type: yes/0
Extra: 01fea9e8328f368f7258bb3b87d861b670a86d9aa6fd7d20cf83cba07aafdc96f8021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.994802226000 dcy

stealth address amount amount idx
00: 3a223e42e5b004a2dc0fc8c7f9328a804650bdd51e57c9b1e9a5476b52ecc109 0.994802226000 1295203 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": 842121, "vin": [ { "gen": { "height": 842111 } } ], "vout": [ { "amount": 994802226, "target": { "key": "3a223e42e5b004a2dc0fc8c7f9328a804650bdd51e57c9b1e9a5476b52ecc109" } } ], "extra": [ 1, 254, 169, 232, 50, 143, 54, 143, 114, 88, 187, 59, 135, 216, 97, 182, 112, 168, 109, 154, 166, 253, 125, 32, 207, 131, 203, 160, 122, 175, 220, 150, 248, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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