Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69da113852e7671b4cb6f39f043448dce9efa8995b8b9eb3166dcf35f7d4dfd6

Tx prefix hash: 49adb16e6bdd95431f3195cba7a469e76676f48d02c81d58fb70d3a566a3a108
Tx public key: 0c87265e333e8099867d284c2c8add06324b8af030ff70f814d88d7351caef1e
Timestamp: 1722067923 Timestamp [UCT]: 2024-07-27 08:12:03 Age [y:d:h:m:s]: 00:309:04:21:52
Block: 1074691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220931 RingCT/type: yes/0
Extra: 010c87265e333e8099867d284c2c8add06324b8af030ff70f814d88d7351caef1e02110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0467493d56fd8fa0254ac1c7f4e77319aebe7f5753b36785122849a815234d5f 0.600000000000 1547208 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": 1074701, "vin": [ { "gen": { "height": 1074691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0467493d56fd8fa0254ac1c7f4e77319aebe7f5753b36785122849a815234d5f" } } ], "extra": [ 1, 12, 135, 38, 94, 51, 62, 128, 153, 134, 125, 40, 76, 44, 138, 221, 6, 50, 75, 138, 240, 48, 255, 112, 248, 20, 216, 141, 115, 81, 202, 239, 30, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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