Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e289bb80a304519f1d821367b99a77e4ae0768e7d5381ce173f6bfa59f44e6f8

Tx prefix hash: 244158a8c8c8d7fa79b5c8226da6adcf827a5155409b3c79ed9004473ed1422a
Tx public key: 58d81df076804dd2e51b49b81d85ff2ae5cdd8090e7d3dc2cbe435a4bf19ab55
Timestamp: 1726608217 Timestamp [UCT]: 2024-09-17 21:23:37 Age [y:d:h:m:s]: 01:021:08:30:08
Block: 1112336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273638 RingCT/type: yes/0
Extra: 0158d81df076804dd2e51b49b81d85ff2ae5cdd8090e7d3dc2cbe435a4bf19ab55021100000003e914dd15000000000000000000

1 output(s) for total of 0.607980000000 dcy

stealth address amount amount idx
00: f4326f33985f5109f2b13b0b55ec21e2bf5a1b3f768e9825e4a06038ccad9a8a 0.607980000000 1591619 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": 1112346, "vin": [ { "gen": { "height": 1112336 } } ], "vout": [ { "amount": 607980000, "target": { "key": "f4326f33985f5109f2b13b0b55ec21e2bf5a1b3f768e9825e4a06038ccad9a8a" } } ], "extra": [ 1, 88, 216, 29, 240, 118, 128, 77, 210, 229, 27, 73, 184, 29, 133, 255, 42, 229, 205, 216, 9, 14, 125, 61, 194, 203, 228, 53, 164, 191, 25, 171, 85, 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