Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dbffcbb995ddf10c3b473205f3b3e1045af08d6fb30695d8e11e602e013f3540

Tx prefix hash: 20944f8772d9a76a0feed19b7f6b92028e983a64649db3caa8cd7b0a80b7c9d5
Tx public key: e6822f389dcbc07128efc3496e461d8a27f25c4e60aadeeaaa7728bcbd975076
Timestamp: 1692292356 Timestamp [UCT]: 2023-08-17 17:12:36 Age [y:d:h:m:s]: 01:192:04:31:47
Block: 828008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398482 RingCT/type: yes/0
Extra: 01e6822f389dcbc07128efc3496e461d8a27f25c4e60aadeeaaa7728bcbd97507602110000000975e3f0e9000000000000000000

1 output(s) for total of 1.107811483000 dcy

stealth address amount amount idx
00: 736c32fc8ba7ee12a6647362d6d850237946eae4e70b83d727fb91058c41f401 1.107811483000 1280328 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": 828018, "vin": [ { "gen": { "height": 828008 } } ], "vout": [ { "amount": 1107811483, "target": { "key": "736c32fc8ba7ee12a6647362d6d850237946eae4e70b83d727fb91058c41f401" } } ], "extra": [ 1, 230, 130, 47, 56, 157, 203, 192, 113, 40, 239, 195, 73, 110, 70, 29, 138, 39, 242, 92, 78, 96, 170, 222, 234, 170, 119, 40, 188, 189, 151, 80, 118, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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