Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15df642fcde2e48137afcefebd3a3768db86137e62b5672abe93889186b5048c

Tx prefix hash: c98516d1087a820a00699906ab88e7a1bb4077a2edb77e4cd4ce375a1773d176
Tx public key: b3d60fb8eb5fef6d6c9fd46758e99a64864f34eb5dfc9f9acc8e140c14fb219a
Timestamp: 1733494839 Timestamp [UCT]: 2024-12-06 14:20:39 Age [y:d:h:m:s]: 00:125:11:33:21
Block: 1169334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89481 RingCT/type: yes/0
Extra: 01b3d60fb8eb5fef6d6c9fd46758e99a64864f34eb5dfc9f9acc8e140c14fb219a021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 551da1e145bdec6254d5545bbcf23a9a4552aa0e1942048490a7d076b7f381bf 0.600000000000 1655049 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": 1169344, "vin": [ { "gen": { "height": 1169334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "551da1e145bdec6254d5545bbcf23a9a4552aa0e1942048490a7d076b7f381bf" } } ], "extra": [ 1, 179, 214, 15, 184, 235, 95, 239, 109, 108, 159, 212, 103, 88, 233, 154, 100, 134, 79, 52, 235, 93, 252, 159, 154, 204, 142, 20, 12, 20, 251, 33, 154, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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