Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63f3be8d6b05556706ed65b3c6e6ff11d67c0145fd1d160d73aabbf756a3234d

Tx prefix hash: 1e723e76d4a6f77d8c87cef95fe90fd5cfb383eb3ba504caeb42fb4482689c81
Tx public key: 4e2b0bcfc55952d0d43a698daa1098bc2ed7d599636e67ec05d13f2ea38bc9d3
Timestamp: 1729157374 Timestamp [UCT]: 2024-10-17 09:29:34 Age [y:d:h:m:s]: 00:005:14:01:12
Block: 1133478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3965 RingCT/type: yes/0
Extra: 014e2b0bcfc55952d0d43a698daa1098bc2ed7d599636e67ec05d13f2ea38bc9d30211000000063cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b49d397bf2107a3fbff68ac297ed45799714c72f40f345b9b4acb1622b2b16b1 0.600000000000 1616601 of 15

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": 1133488, "vin": [ { "gen": { "height": 1133478 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b49d397bf2107a3fbff68ac297ed45799714c72f40f345b9b4acb1622b2b16b1" } } ], "extra": [ 1, 78, 43, 11, 207, 197, 89, 82, 208, 212, 58, 105, 141, 170, 16, 152, 188, 46, 215, 213, 153, 99, 110, 103, 236, 5, 209, 63, 46, 163, 139, 201, 211, 2, 17, 0, 0, 0, 6, 60, 208, 252, 6, 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