Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b27b8fccf62cd6e957504c2a51aca37345c0618b436ecff11b92a8c5c691617

Tx prefix hash: f4890ef4b7dc6afcaddcc398af04bc27e650e9b33968c815cebbd01098b1b8af
Tx public key: 9a18ddbfe78ffc6a9868c7d402c18a69d521184e78c8c23eec22dad1e50791f2
Timestamp: 1729012779 Timestamp [UCT]: 2024-10-15 17:19:39 Age [y:d:h:m:s]: 00:039:05:30:20
Block: 1132276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28005 RingCT/type: yes/0
Extra: 019a18ddbfe78ffc6a9868c7d402c18a69d521184e78c8c23eec22dad1e50791f2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3162c8be3d197d782d479d1cf42279035efd41a2b13e1b59fbdd0644b959d39f 0.600000000000 1615189 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": 1132286, "vin": [ { "gen": { "height": 1132276 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3162c8be3d197d782d479d1cf42279035efd41a2b13e1b59fbdd0644b959d39f" } } ], "extra": [ 1, 154, 24, 221, 191, 231, 143, 252, 106, 152, 104, 199, 212, 2, 193, 138, 105, 213, 33, 24, 78, 120, 200, 194, 62, 236, 34, 218, 209, 229, 7, 145, 242, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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