Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ea4ed728561b7fdaeb7ec79171e9ec2f6c774ac29309f294a1d3588304e9e64

Tx prefix hash: c931a11d79f186ca6a2a1eb59ae2b90d8d57eff946e32a12aa21ac66d606e742
Tx public key: 7f47072f470e8ab33f3302b0e9933624dfadcd9b59ba7ca602251ed9b583005a
Timestamp: 1582363572 Timestamp [UCT]: 2020-02-22 09:26:12 Age [y:d:h:m:s]: 05:101:02:15:20
Block: 70156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1225449 RingCT/type: yes/0
Extra: 017f47072f470e8ab33f3302b0e9933624dfadcd9b59ba7ca602251ed9b583005a021100000049d81c26c0000000000000000000

1 output(s) for total of 359.378719488000 dcy

stealth address amount amount idx
00: fed92d2a087db3eca30575f2ec17ce3f83ba8f9c794edae5d8f8600fc3bca530 359.378719488000 129512 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": 70166, "vin": [ { "gen": { "height": 70156 } } ], "vout": [ { "amount": 359378719488, "target": { "key": "fed92d2a087db3eca30575f2ec17ce3f83ba8f9c794edae5d8f8600fc3bca530" } } ], "extra": [ 1, 127, 71, 7, 47, 71, 14, 138, 179, 63, 51, 2, 176, 233, 147, 54, 36, 223, 173, 205, 155, 89, 186, 124, 166, 2, 37, 30, 217, 181, 131, 0, 90, 2, 17, 0, 0, 0, 73, 216, 28, 38, 192, 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