Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4330fd7865bf52634fd9e92b55350663eb7d66cf1efa35684361ab4ca52545c

Tx prefix hash: cf7af46781dca2bf497ec60cb32a2aecc1e95ad827e40bb2061355cefe357568
Tx public key: ace0d7b0cbd319094ca48a4fe1fff0418f7501dce33bad1fba79edf3a51f67dd
Timestamp: 1713648772 Timestamp [UCT]: 2024-04-20 21:32:52 Age [y:d:h:m:s]: 00:218:05:52:45
Block: 1004894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156239 RingCT/type: yes/0
Extra: 01ace0d7b0cbd319094ca48a4fe1fff0418f7501dce33bad1fba79edf3a51f67dd0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c0b007d3da255fd37fb5ce523b70d820f0457e2e1d299c9f2f0f68e87a5c1d8 0.600000000000 1465468 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": 1004904, "vin": [ { "gen": { "height": 1004894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c0b007d3da255fd37fb5ce523b70d820f0457e2e1d299c9f2f0f68e87a5c1d8" } } ], "extra": [ 1, 172, 224, 215, 176, 203, 211, 25, 9, 76, 164, 138, 79, 225, 255, 240, 65, 143, 117, 1, 220, 227, 59, 173, 31, 186, 121, 237, 243, 165, 31, 103, 221, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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