Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6886c387ac5387e7531526e753ecb8e809136c63c953fe389ecf8bba0748f80d

Tx prefix hash: 1c0a50254a6a6de86750c808b5d5232a47fb3c4eee2f51ac79f37f7511e98c10
Tx public key: 2eb707474d0d70a4a173605a9d00329cd1fd5de6f82aff4d128d6c06c2299e39
Timestamp: 1735915950 Timestamp [UCT]: 2025-01-03 14:52:30 Age [y:d:h:m:s]: 00:162:17:33:54
Block: 1189385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116029 RingCT/type: yes/0
Extra: 012eb707474d0d70a4a173605a9d00329cd1fd5de6f82aff4d128d6c06c2299e390211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37503d4d83a4b52657d5346b680496d8ffd87fe5eac9c239f66b5af0b39c5125 0.600000000000 1675894 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": 1189395, "vin": [ { "gen": { "height": 1189385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37503d4d83a4b52657d5346b680496d8ffd87fe5eac9c239f66b5af0b39c5125" } } ], "extra": [ 1, 46, 183, 7, 71, 77, 13, 112, 164, 161, 115, 96, 90, 157, 0, 50, 156, 209, 253, 93, 230, 248, 42, 255, 77, 18, 141, 108, 6, 194, 41, 158, 57, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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