Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f5f51689a8299fc85b86683fb65fd2adb969e3ffa4184c813f16e01429f0bb

Tx prefix hash: 2872e26bdebd03ab808c84d044acc7e00d80da5cc8a3af5759d8e4b61a8165df
Tx public key: cf52263c457f84028420fef5c556a69b695e8c1fe871972c6b4c0e4f74d7da25
Timestamp: 1708138751 Timestamp [UCT]: 2024-02-17 02:59:11 Age [y:d:h:m:s]: 01:049:03:04:43
Block: 959212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296151 RingCT/type: yes/0
Extra: 01cf52263c457f84028420fef5c556a69b695e8c1fe871972c6b4c0e4f74d7da250211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 235365a11a59a6b37b3994be1da24172e8a86f18b8e83f0b596b1876e68ace26 0.600000000000 1418743 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": 959222, "vin": [ { "gen": { "height": 959212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "235365a11a59a6b37b3994be1da24172e8a86f18b8e83f0b596b1876e68ace26" } } ], "extra": [ 1, 207, 82, 38, 60, 69, 127, 132, 2, 132, 32, 254, 245, 197, 86, 166, 155, 105, 94, 140, 31, 232, 113, 151, 44, 107, 76, 14, 79, 116, 215, 218, 37, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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