Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 109a194ae05ba7dd09d31b0dc6c35d421f22d045181c50c1a5967775634d28f7

Tx prefix hash: 83ad9e1e819ee5e9c88089806c62d31a74c2ace61f3a700ee6da68ade311abea
Tx public key: f477dffa0ce1c1350a55daa79d8bef5ad989c08b746b3da9e060776a4d466e4d
Timestamp: 1708469799 Timestamp [UCT]: 2024-02-20 22:56:39 Age [y:d:h:m:s]: 01:118:03:26:56
Block: 961964 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345391 RingCT/type: yes/0
Extra: 01f477dffa0ce1c1350a55daa79d8bef5ad989c08b746b3da9e060776a4d466e4d02110000000d52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f83aaff85322c52ec7acb94526a3089a25060bea534fd88ae6c48af42c575d5 0.600000000000 1421585 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": 961974, "vin": [ { "gen": { "height": 961964 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f83aaff85322c52ec7acb94526a3089a25060bea534fd88ae6c48af42c575d5" } } ], "extra": [ 1, 244, 119, 223, 250, 12, 225, 193, 53, 10, 85, 218, 167, 157, 139, 239, 90, 217, 137, 192, 139, 116, 107, 61, 169, 224, 96, 119, 106, 77, 70, 110, 77, 2, 17, 0, 0, 0, 13, 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