Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 915fd7f105d7e2ed6dedf1bc59c89053e54e126b26d93514c38a86d9bb0c4c1f

Tx prefix hash: 8fc20fcd066cf1025ff22938fee31d2e59316a9dc63c03b1a8cee2ad935999f2
Tx public key: 0b107f5850a550a0350e55a0a49467c2b8d9b58e17afc5a3a66b99ca034e6c01
Timestamp: 1710142134 Timestamp [UCT]: 2024-03-11 07:28:54 Age [y:d:h:m:s]: 00:350:22:55:26
Block: 975841 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 250904 RingCT/type: yes/0
Extra: 010b107f5850a550a0350e55a0a49467c2b8d9b58e17afc5a3a66b99ca034e6c0102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ad48281c03d0eb92e252ead9eee74d3f029a57ca45fefd91648e863591c9f17 0.600000000000 1435818 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": 975851, "vin": [ { "gen": { "height": 975841 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ad48281c03d0eb92e252ead9eee74d3f029a57ca45fefd91648e863591c9f17" } } ], "extra": [ 1, 11, 16, 127, 88, 80, 165, 80, 160, 53, 14, 85, 160, 164, 148, 103, 194, 184, 217, 181, 142, 23, 175, 197, 163, 166, 107, 153, 202, 3, 78, 108, 1, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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