Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6f5748e90950fc4d191f4a7cc7d33a21da8d56b009fddbf955fe992bde85f7c

Tx prefix hash: f7ba8664cf2ec7bef31c45d7a7c1a8e3195b04b2765665524fc187d14fe1a46f
Tx public key: 052f9ef14d1d353c0b45edcbe837bf8009046214acb209c120aeef2b43c07cb6
Timestamp: 1651418368 Timestamp [UCT]: 2022-05-01 15:19:28 Age [y:d:h:m:s]: 02:240:01:36:39
Block: 492157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 691550 RingCT/type: yes/0
Extra: 01052f9ef14d1d353c0b45edcbe837bf8009046214acb209c120aeef2b43c07cb6021100000002d3fcec30000000000000000000

1 output(s) for total of 14.364144716000 dcy

stealth address amount amount idx
00: e8ec7c139483eb1a0cdce053b0aa2356391e6d090a57408167282cdd736693cc 14.364144716000 915440 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": 492167, "vin": [ { "gen": { "height": 492157 } } ], "vout": [ { "amount": 14364144716, "target": { "key": "e8ec7c139483eb1a0cdce053b0aa2356391e6d090a57408167282cdd736693cc" } } ], "extra": [ 1, 5, 47, 158, 241, 77, 29, 53, 60, 11, 69, 237, 203, 232, 55, 191, 128, 9, 4, 98, 20, 172, 178, 9, 193, 32, 174, 239, 43, 67, 192, 124, 182, 2, 17, 0, 0, 0, 2, 211, 252, 236, 48, 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