Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f5aeedf1b51db6c468d24b4b472aac24393abf0740aa7df20be20020cb2467

Tx prefix hash: a8797b24c407fc869459da6d35233775ef2f69c4a6454d8fc12776ab41c73e96
Tx public key: 7f185eebd4f045e362c883691de727e200e06299ef41a4afbb8d47dd219c2602
Timestamp: 1698399979 Timestamp [UCT]: 2023-10-27 09:46:19 Age [y:d:h:m:s]: 01:092:18:35:41
Block: 878698 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327289 RingCT/type: yes/0
Extra: 017f185eebd4f045e362c883691de727e200e06299ef41a4afbb8d47dd219c26020211000000084b8f5122000000000000000000

1 output(s) for total of 0.752503936000 dcy

stealth address amount amount idx
00: d22dce9728dac31e3b1a7c9c4ca0e1ec2e30f989a9a795229cddc31263b0d647 0.752503936000 1334170 of 0

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": 878708, "vin": [ { "gen": { "height": 878698 } } ], "vout": [ { "amount": 752503936, "target": { "key": "d22dce9728dac31e3b1a7c9c4ca0e1ec2e30f989a9a795229cddc31263b0d647" } } ], "extra": [ 1, 127, 24, 94, 235, 212, 240, 69, 227, 98, 200, 131, 105, 29, 231, 39, 226, 0, 224, 98, 153, 239, 65, 164, 175, 187, 141, 71, 221, 33, 156, 38, 2, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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