Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b73680143267751d71f4324be7af4dd5e1fc95290b963a692c77676634999cb

Tx prefix hash: 18a77687b69fb440f2296dd4ef66c8d7cca4dc5dc19b14ae6cbae3ee146bd6fc
Tx public key: f7d4b306ca6f09f8332070895ed37dee6d34f3e5eab6f0909fc6191d99ef6d77
Timestamp: 1716451205 Timestamp [UCT]: 2024-05-23 08:00:05 Age [y:d:h:m:s]: 00:300:15:35:55
Block: 1028138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214899 RingCT/type: yes/0
Extra: 01f7d4b306ca6f09f8332070895ed37dee6d34f3e5eab6f0909fc6191d99ef6d7702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a3ff5d0ee405f7ee0c1841537fdd3e250aa4cb8000d8e37400c5409653073fd 0.600000000000 1496075 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": 1028148, "vin": [ { "gen": { "height": 1028138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a3ff5d0ee405f7ee0c1841537fdd3e250aa4cb8000d8e37400c5409653073fd" } } ], "extra": [ 1, 247, 212, 179, 6, 202, 111, 9, 248, 51, 32, 112, 137, 94, 211, 125, 238, 109, 52, 243, 229, 234, 182, 240, 144, 159, 198, 25, 29, 153, 239, 109, 119, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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