Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69af75fad86e78a2ce6ccc718762c5a0bb5ca90745e4d565b597d16198b2ea2e

Tx prefix hash: 4adaa4ad50d3b8479b18135ecacd38397efc5beb04764a49774b818f2e0348c5
Tx public key: 1344df57d0607fb9cb91609e82006492590cb36f4d5c5c42c06c2040e7eedafb
Timestamp: 1719183312 Timestamp [UCT]: 2024-06-23 22:55:12 Age [y:d:h:m:s]: 00:268:12:31:44
Block: 1050776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191896 RingCT/type: yes/0
Extra: 011344df57d0607fb9cb91609e82006492590cb36f4d5c5c42c06c2040e7eedafb0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f651b8cf14bd50694d96df08b8b2db6d1396aa0ec1fc8e6448ea9a483381b317 0.600000000000 1520951 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": 1050786, "vin": [ { "gen": { "height": 1050776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f651b8cf14bd50694d96df08b8b2db6d1396aa0ec1fc8e6448ea9a483381b317" } } ], "extra": [ 1, 19, 68, 223, 87, 208, 96, 127, 185, 203, 145, 96, 158, 130, 0, 100, 146, 89, 12, 179, 111, 77, 92, 92, 66, 192, 108, 32, 64, 231, 238, 218, 251, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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