Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c854e02e68c5d6dbb5f97f9ca33dc3da6ab31d17cfa38c64cbe0c4f316d4456b

Tx prefix hash: 06c3bc1e87bf01a8fffee0ccf7640c0a50c3c5170a3e4666839da385f7793b9a
Tx public key: d3fe847514123d4ff8adac9b4ee18de0717fea702ab47097cfdbe62bad320e73
Timestamp: 1702708479 Timestamp [UCT]: 2023-12-16 06:34:39 Age [y:d:h:m:s]: 01:035:10:14:29
Block: 914198 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286640 RingCT/type: yes/0
Extra: 01d3fe847514123d4ff8adac9b4ee18de0717fea702ab47097cfdbe62bad320e73021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4a6b5807fc8614a578e0c4bbcc26bbb9afe3904b73283baa0d27c78e42c2b15 0.600000000000 1371484 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": 914208, "vin": [ { "gen": { "height": 914198 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4a6b5807fc8614a578e0c4bbcc26bbb9afe3904b73283baa0d27c78e42c2b15" } } ], "extra": [ 1, 211, 254, 132, 117, 20, 18, 61, 79, 248, 173, 172, 155, 78, 225, 141, 224, 113, 127, 234, 112, 42, 180, 112, 151, 207, 219, 230, 43, 173, 50, 14, 115, 2, 17, 0, 0, 0, 3, 250, 243, 92, 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